feat: Add multi-repo switching support with server backend integration#148
feat: Add multi-repo switching support with server backend integration#148Rocky0102 wants to merge 3 commits into
Conversation
- Add currentRepoName state tracking in useAppState for repo context - Update initializeAgent to accept overrideRepoName parameter for server mode - Implement server-mode query execution with repo parameter in runQuery - Fix HTTP endpoint paths in ingestion worker (remove duplicate /api prefix) - Increase agent recursion limit from 50 to 200 for complex multi-step reasoning - Pass repo context through App.tsx handleServerConnect callback Enables seamless switching between multiple indexed repositories when connected to a server backend, with proper repo context propagation through query execution and agent initialization.
|
@srocky2035-hash is attempting to deploy a commit to the NexusCore Team on Vercel. A member of the Team first needs to authorize it. |
- Implement resizable left/right panels with ResizableDivider component
- Left panel (file tree): 200-600px range
- Right panel (code/chat): 400-800px range
- Add per-repo chat session management with server-side persistence
- Sessions organized by repository (repoName field)
- Auto-save sessions on task completion
- Save sessions before clearing or switching repos
- Load/delete/refresh session functionality per repo
- Store sessions in separate files: ~/.gitnexus/sessions/{repoName}.json
- No quantity limit - all sessions per repo are preserved
- Add backend API endpoints: GET/POST/DELETE /api/sessions
- Preserve tool call args in UI display
- Add args property to ToolCallInfo type
- Display tool arguments in ToolCallCard component
|
Second Commit:
|
2. session history: save separately by repo with individual files per session 3. rename Clear button to New to better reflect starting a new session
|
|
Please submit a new PR if this is still relevant |
Fixed problem: when use web UI to connect to backend server (4747 port), cypher query and AI chat not working, reporting KuzuDB error/repo not loaded.
Enables seamless switching between multiple indexed repositories when connected to a server backend, with proper repo context propagation through query execution and agent initialization.